Three first-hop destinations opened from the Projects header: Fleet, Review Center and Settings. One system for all three — a standard back, a large title, a factual summary line, then low-container rows. Six frames show the highest-risk state of each surface rather than its happy path. Entry Flow Master v2 is unchanged; this board decides how its header's destinations look.
Standard back at the gutter, large title, one factual summary line. The summary counts what the backend reported and nothing else.
Shape, written status, name, then real activity. The badge is semantic and counts pending approvals only. The whole row is the target.
Circle, diamond, square, ring — the same four marks the locked direction already uses. Each is always beside its word.
Three tabs as bordered chips that wrap instead of clipping. Category rows carry a summary drawn from live settings — never a secret, never a guess.
Back, large title, one factual summary line, then rows. The three destinations then feel like one product rather than three teams' work, and a user who has learnt one has learnt the others. The variation that matters — an attention strip, a tab control, a category list — sits below the header where it belongs.
Fleet attention and the Review inbox both divide into what needs a person and what is already settled, under written section labels. It is the same rule the approval work already follows, and it survives translation and large type without any layout cleverness.
A badge, a diamond or an accent dot appears only where the backend supplied the condition behind it — pending counts, an active full-control expiry, an available update. Everything else stays quiet, which is what makes the few marks readable.
Every name, path, count, title, timestamp and version on this board is a fixture chosen to stress the layout: the four computers, the two pending requests, the five reviews, the three scheduled tasks, the 12-hour expiry. None asserts how the product behaves. The only real product vocabulary here is the five review states, the four connection states, the field names and the category contents.
Expand into an interactive master the way the entry flow was: one device component, one state machine, every route live — Fleet switching computers, the attention list answering requests, three tabs, five categories and their drill-downs. The frames on this board are already the states that master has to hold.